• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch update

Reviewing files that changed from the base of the PR and between 23e66b6 and e4b4a2b.

• pnpm-lock.yaml is excluded by !**/pnpm-lock.yaml

• package.json (2 hunks)
• packages/queue/package.json (2 hunks)
• pnpm-workspace.yaml (1 hunks)

packages/queue/package.json (2)

20-27: ⚠️ Breaking change: Exports map now ESM-only

The removal of the "require" field from the exports map makes @nextorders/queue an ESM-only package. This is a breaking change for any CommonJS consumers. Since the package is marked "type": "module", this aligns with that declaration, but it should be:

• Documented in the CHANGELOG
• Reflected in a major version bump (currently 0.3.0)
• Communicated to users who rely on CommonJS imports

Verify this is intentional and expected.

---

36-37: ✓ Good: Clean scripts align with monorepo pattern

The addition of clean and clean:modules scripts follows the established pattern in the root package.json and provides explicit cleanup targets.

pnpm-workspace.yaml (3)

32-34: ✓ Good: publicHoistPattern updated consistently

Removal of vitest-browser-vue from publicHoistPattern aligns with its removal from the development dependencies.

---

24-26: ****

The original concern mischaracterizes what ignoredBuiltDependencies does—it suppresses warnings about packages not being built and skips their build scripts, but the packages are still installed. Since unbuild explicitly depends on esbuild (version ^0.25.8), adding esbuild to ignoredBuiltDependencies will not break builds. The package will remain available; only its native module compilation will be skipped, which is acceptable for this use case.

Likely an incorrect or invalid review comment.

---

7-7: Configuration is technically compatible with @antfu/eslint-config v6.0.0

The codebase already uses the flat-config model (eslint.config.mjs) required by v6, and ESLint ^9.38.0 satisfies the v9.5.0+ peer dependency. The configuration syntax is correct for v6.

However, manual verification is still needed: v6 may introduce stricter rules that cause new linting errors. Please run npm run lint (or pnpm lint) after upgrading to confirm no new violations are introduced.

package.json (2)

17-17: No issues found — build tool migration is safe

Verification confirms the repository contains no .vue files and vue-tsc has been cleanly removed from devDependencies. The change from vue-tsc to tsc is appropriate for this TypeScript-only project and poses no risk to type generation. The single Vue reference in package.json is only in the lint-staged file pattern and does not indicate Vue dependency.

---

31-43: Original review comment is incorrect and should be disregarded.

The claimed removed tools (tsx, vite, vitest-browser-vue, vue-tsc) are not present in the current package.json devDependencies and do not appear to be removed by this PR. Evidence:

• No npm scripts invoke these tools directly: All test scripts use only vitest (lines 25-28), which is retained in devDependencies.
• No CI/CD files exist that reference these tools.
• vitest-browser-vue does not exist anywhere in the repository.
• The .tsx reference on line 46 is merely a glob pattern in lint-staged configuration for matching file extensions, not a tool invocation.

All test dependencies are correctly maintained and functional.

Likely an incorrect or invalid review comment.